kermit.columbia.edu/kermit.columbia.edu.tar/kermit.columbia.edu/newsgroups/misc.20041116-20060924/[e-mail]_Sun Mar 19 14:58:46 2006.msg

Internet Message Format | 2006-09-27 | 4KB

Path: newsmaster.cc.columbia.edu!panix!logbridge.uoregon.edu!arclight.uoregon.edu!wns13feed!worldnet.att.net!207.35.177.252!nf3.bellglobal.com!ursa-nb00s0.nbnet.nb.ca!53ab2750!not-for-mail
From: "Scott Caissie" <[e-mail]>
Newsgroups: comp.protocols.kermit.misc
References: <uGRPf.40748$[e-mail]> <kLSPf.9392$[e-mail]> <[e-mail]> <RqZPf.40942$[e-mail]> <[e-mail]> <H81Qf.41050$[e-mail]> <ok2Qf.12766$[e-mail]> <aQkQf.41491$[e-mail]> <pVlQf.14280$[e-mail]> <ATwQf.41716$[e-mail]> <s3CQf.15925$[e-mail]> <vmPQf.42198$[e-mail]> <3CVQf.10658$[e-mail]> <KaQRf.43750$[e-mail]> <EWZRf.18631$[e-mail]>
Subject: Re: closing a macro completely upon connect
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <Hq%Rf.43986$[e-mail]>
Date: Wed, 15 Mar 2006 21:12:07 GMT
NNTP-Posting-Host: 156.34.25.154
X-Complaints-To: [e-mail]
X-Trace: ursa-nb00s0.nbnet.nb.ca 1142457127 156.34.25.154 (Wed, 15 Mar 2006 17:12:07 AST)
NNTP-Posting-Date: Wed, 15 Mar 2006 17:12:07 AST
Organization: Aliant Internet
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15529

Can you clarify your own posts? A few things are bothering me still.

Macros only execute in "command mode".  Its been several years since I
fixed the bug associated with SET KEY and terminal mode, but my
recollection is that the macro would be configured to execute and
"terminal or connect mode" would not be exited.

1. First sentence we know is wrong. Partially. The example I gave you  by
invoking a macro as a kverb works. Same example that you posted afterwards
as well. It has the ability to leave connect mode on its own and runs the
macro. A bridge is created.
2. Rest of your paragraph explains everything that I'm looking for.

A macro mapped to a key will not execute if you enter CONNECT mode
directly.   As described in the newbugs.txt file
  * Fixed a bug preventing the execution of macros assigned to keys or
    mouse events when in terminal mode

3. Please don't say nesting. Don't even need to include Frank da Cruz's bug
description on this one. Your own bug description says its not possible to
begin with, so nesting never comes into play.

because as far as I am aware the macro is never executed when bound to a key
and the key is pressed while in CONNECT mode

4. Here you say it can't be done. You are now using my very own example to
say that the Kverb method is the proper way, though previously mentioned as
a 'work around' and a 'hack'.


Ya I get the picture that a macro won't actively run while in connect mode.
An amazing loss of potential there.
I HAVE been re-reading what you are writting. I don't think you are proof
reading it.
Which is why I was confused as hell, and wondering what is a bug or not. You
had me half convinced that this feature is a bug, or a hack. Which is why I
was concerned of it being 'fixed'.

But I have little worry in that now.
It is unfortunate to learn of K95's limits. I had such high hopes there.
They were real hopes too. I'm not kidding you. You get the book on how to
use the software. Only problem is that nothing in the book works without
using a hack, as you say, and even that apparently doesn't work right, when
you are using the software in any real productive way. But I do understand
how old k95 is.
I'm still going to keep trying to push out its potential here beyond the
normal use. If you guys could modify VIEWONLY perhaps? So that it is what it
does. It is the CONNECT command that disables modifying anything. Its pauses
the macro.It would give the users the illusion of the screen not changing.
That itself would be enough to create a seemless use of a greater potential
here.

example:
define test {
viewonly
; coding which isn't being paused
connect /synchronous ; would effectively override viewonly.
}